Release 10.1A: OpenEdge Development:
Web Services

Memory for the SOAP header object model and DOM

Table 11–1 summarizes the available 4GL elements and how they can help you to manage memory for SOAP headers.

Table 11–1: 4GL to manage object memory for SOAP headers 

4GL element	Applied to object	Deletes the 4GL object	Deletes all underlying XML DOM objects
Setting the lDeleteOnDone OUTPUT parameter of the request header handler to TRUE (see the "Defining header handlers" section.	SOAP header object.	Yes	Yes
DELETE OBJECT statement.	SOAP header object.	Yes	Yes
	X-document object.	Yes	Yes
	SOAP header-entryref object.	Yes	No
	X-noderef object.	Yes	No
DELETE-HEADER-ENTRY( ) method.	SOAP header-entryref object.	No	Yes1
DELETE-NODE( ) method.	X-noderef object.	No	Yes1

1This includes any child sub-trees of the deleted X-noderef object.

Caution: Be sure that you always delete the underlying XML for a SOAP header-entryref object before you delete the SOAP header-entryref object itself. If you lose all reference to the underlying XML before deleting it, its memory becomes lost to your application. If this occurs as part of an iterative process, it represents a memory leak that could cause your application to crash.